The rationale here is that package.yaml files can get quite complex,
specifically in regards to anchors. Instead, we should just call out
to 'stack build --dry-run' to generate the cabal files, which will also
verify that our build configuration is valid, then we can just parse
each cabal file into a PackageConfig.

…r to get around needing an Application in the externalSystem

…exExcludePolicy

…per package

…JVM processes

…e key)

… modifying stack.yaml

…n project

…e is modified

…ingsUpdater

…to-import feature

…rt time

Was previously wrapped in an erroneous 'getPkgs' call which would
always be None if the ghc-pkg cache had not been previously loaded.

It seems like this check should be pointless since the file 'f' in
question was found in the module name index.

…dule"

This reverts commit e8c3fe9.

…ludePolicy

In a previous commit, we changed HaskellBuildSettings to no longer
auto-guess the exe if it was not set. This broke some assumptions made
by our new project wizard in HaskellModuleBuilder. Fixed this by doing
the guessing manually.